THIS DOCUMENT CONTAINS SOME HELP ON CREATING YOUR OWN CUSTOMDESKS 
FOR THE VMIDIBOX TOOLS...

there is a button to load *.vmb files. 
(this is just a different extension for the same ini files). 
By default, customdesk.vmb is used when it is found in the application directory. 
The intention is to make it possible to have a collection of .vmb files 
in a 'customfiles' subdirectory of the application directory. 

---------



DECIMAL COLOR CODING INFO :
-----------------------------
The formula is :

Blue*256*256 +  Green * 256 + Red
This is easily calculated in hex :
    for example : Red = 0x61, Green = 0x1F, Blue =  0x31.
color value = 0x311f61 (hex) == 3219297 (decimal)

By using an editor such as ultraedit, you can see and edit  the color value
on a visual palette directly.
---------


Virtual Midibox64 Tag Memory Map
---------------------------------

0   		Reserved
1 - 256 	Pots
257 - 999 	Reserved for Pots Expansion
1000		Reserved
1 - 256 	Buttons
257 - 1999 	Reserved for Button Expansion
2000		Reserved
2001 - 2999	Passive controls (such as labels)
... ???

----



EXAMPLE : HOW TO CREATE LABELED BUTTONS THAT ALLOW BANKSWITCHING :
--------------------------------------------------------------------
here's how you can do this : 
first create a sysex file with vmidibox that uses 16  
buttons to select each of the banks. 
(code is : (see presetlist)) 
FF 02 0n | Switch to BankStick Bank n (n = 0..F) 
 
You can test this first in connection with your real mb64. 
 
If this is OK, modify the matching button code in vcustombox.vmb 
 
for example for button 1 change the following code : 
[Button_136] 
Type=Button 
Caption=1 
Tag=1001 
Height=25 
Width=25 
Left=38 
Top=380 
 
You can see that the tag value is '1001' : this links the button to the matching action 01 and should not be changed. Also the type should stay 'Button' 
 
The other properties may be changed as you wish : 
The value for caption should contain the name if the bank. 
 
 
You can easily delete all redundant button and fader code, but keep the form and LCD display data !. 
 
---------

skinning sample code:


[KnobSkin_01]
Type=KnobSkin
Tag=9005
Left=30
Top=60
FileName=TIWoriginalKnobSkin.bmp

[ButtonSkin_01]
Type=ButtonSkin
Tag=9006
Left=30
Top=60
FileName=TestBounceButt.bmp

[SkinKnob_86]
Type=SkinKnob
SkinImageCount=64
SkinID=1
Caption=
Tag=19
Height=40
Width=40
Left=130
Top=175

[Button_195]
Type=SkinButton
SkinImageCount=6
SkinID=0
Interval=4
Caption=
SwitchStyle=0
Tag=1064
Height=25
Width=25
Left=588
Top=520
Transparent=1





since version 1.00f the following settings can be used in vmb files :

[APPLICATIONPRESETS]
MIDIINPORT=8
MIDIOUTPORT=9
SYSEXSENDSPEED=200
[CUSTOMDESK]
FILENAME=self
AUTOSHOW=1
EDITORHIDE=1
[CUSTOMSYSEX]
FILENAME=fabtest1.syx













-------------
EXAMPLE: DIPSWITCH : USEFUL FOR CONTROLLING THE SIDMODULE ?  04.10.02

Support will be implemented for a virtual dipswitch. 
THIS IS NOT FUNCTIONAL YET !!!
Sample code :

[DipSwitch_01]
Type=DipSwitch
Tag=16
Height=100
Width=100
Left=580
Top=16
BitCount=7
BitOnLabel0=  Triangle ON
BitOffLabel0= Triangle OFF
BitOnLabel1= Saw ON
BitOffLabel1= Saw OFF
BitOnLabel2= Pulse ON
BitOffLabel2= Pulse OFF
BitOnLabel3= Noise ON
BitOffLabel3= Noise OFF
BitOnLabel4=  Voice OFF
BitOffLabel4= Voice ON
BitOnLabel5= Sync ON
BitOffLabel5= Sync OFF
BitOnLabel6= Ring ON
BitOffLabel6= Ring OFF



